Skip to content

chore: release 12.0.0-pre.0.0#9229

Open
github-actions[bot] wants to merge 1 commit intolatestfrom
release-please--branches--latest
Open

chore: release 12.0.0-pre.0.0#9229
github-actions[bot] wants to merge 1 commit intolatestfrom
release-please--branches--latest

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions Bot commented Apr 13, 2026 •
edited
Loading

🤖 I have created a release beep boop

12.0.0-pre.0.0

12.0.0-pre.0.0 (2026-05-06)

⚠️ BREAKING CHANGES

  • npm view --json now always returns an array.
  • npm sbom --sbom-format=cyclonedx now reports the name field from each package's package.json instead of the on-disk directory name. The name, bom-ref, and purl of the root component and of aliased dependencies may change.
  • npm no longer registers man pages with the system when installed globally. man npm-install will no longer work, but npm help install is unaffected.
  • The npm pkg output is no longer forced to json. This means you can get single values without having to worry about wrapping of the values. It also outputs non-json content more similarly to npm view.
  • npm shrinkwrap is removed, the shrinkwrap config alias is removed, and npm-shrinkwrap.json is no longer loaded or honored at the project root or from inside dependency tarballs. Rename project-root npm-shrinkwrap.json to package-lock.json; use bundleDependencies if you need to ship a locked dependency tree.
  • The Twitter and Freenode profile fields have been removed from the npm registry. This means that users will no longer be able to set or view these fields in their npm profiles.
  • npm will no longer attempt to resolve the path to node via whichnode. process.execPath is already set by Node to the resolved real path of the node binary, so the lookup was redundant. Scripts that expected npm to override process.execPath with a PATH-resolved (potentially symlinked) node path may be affected.
  • the --json output of npm pack and npm publish have changed. They are now always consistent, and in the same format.
  • the star, stars and unstar commands have been removed
  • The npm adduser command has been removed. Create and manage user accounts on the npm website, and use npm login to authenticate on the command line.

Features

Bug Fixes

Dependencies

Chores

arborist: 10.0.0-pre.0.0

10.0.0-pre.0.0 (2026-05-06)

⚠️ BREAKING CHANGES

  • npm shrinkwrap is removed, the shrinkwrap config alias is removed, and npm-shrinkwrap.json is no longer loaded or honored at the project root or from inside dependency tarballs. Rename project-root npm-shrinkwrap.json to package-lock.json; use bundleDependencies if you need to ship a locked dependency tree.

Features

Bug Fixes

config: 11.0.0-pre.0.0

11.0.0-pre.0.0 (2026-05-06)

⚠️ BREAKING CHANGES

  • npm shrinkwrap is removed, the shrinkwrap config alias is removed, and npm-shrinkwrap.json is no longer loaded or honored at the project root or from inside dependency tarballs. Rename project-root npm-shrinkwrap.json to package-lock.json; use bundleDependencies if you need to ship a locked dependency tree.

Features

Bug Fixes

libnpmdiff: 8.1.6-pre.0.0

Dependencies

libnpmexec: 10.2.6-pre.0.0

10.2.6-pre.0.0 (2026-05-06)

Bug Fixes

Chores

Dependencies

libnpmfund: 7.0.20-pre.0.0

Dependencies

libnpmpack: 10.0.0-pre.0.0

10.0.0-pre.0.0 (2026-05-06)

⚠️ BREAKING CHANGES

  • npm pack and npm publish now error when a package's overrides apply to one or more of its bundled packages (bundledDependencies / bundleDependencies). Defining both fields is still allowed as long as no override actually targets a bundled package. To resolve the error, remove the affected entries from either overrides or the bundle.

Bug Fixes

Dependencies

libnpmversion: 9.0.0-pre.0.0

9.0.0-pre.0.0 (2026-05-06)

⚠️ BREAKING CHANGES

  • npm shrinkwrap is removed, the shrinkwrap config alias is removed, and npm-shrinkwrap.json is no longer loaded or honored at the project root or from inside dependency tarballs. Rename project-root npm-shrinkwrap.json to package-lock.json; use bundleDependencies if you need to ship a locked dependency tree.

Features

Chores

This PR was generated with Release Please. See documentation.

@github-actions github-actions Bot requested a review from a team as a code owner April 13, 2026 21:46
@github-actions
Copy link
Copy Markdown
Contributor Author

github-actions Bot commented Apr 13, 2026 •
edited
Loading

Release Manager

Release workflow run: https://github.com/npm/cli/actions/runs/25454145455

Release Checklist for v12.0.0-pre.0.0

  • 1. Checkout the release branch

    Ensure git status is not dirty on this branch after resetting deps. If it is, then something is probably wrong with the automated release process.

    gh pr checkout 9229 --force
    npm run resetdeps
    node scripts/git-dirty.js

  • 2. Check CI status

    gh pr checks --watch

  • 3. Log in to npm

    npm login sessions are short lived, so you will want to have a fresh one before you publish.

    npm login

  • 4. Publish the CLI and workspaces

    Warning:
    This will publish all updated workspaces to latest, prerelease or backport depending on their version, and will publish the CLI with the dist-tag set to next-12.

    Note:
    The --test argument can optionally be omitted to run the publish process without running any tests locally.

    node scripts/publish.js --test

  • 5. Optionally install and test npm@12.0.0-pre.0.0 locally

    npm i -g npm@12.0.0-pre.0.0
    npm --version
npm whoami
npm help install
# etc

  • 6. Trigger docs.npmjs.com update

    gh workflow run update-cli.yml --repo npm/documentation

  • 7. Approve and Merge release PR

    gh pr review --approve
    gh pr merge --rebase
    git checkout latest
    git fetch
    git reset --hard origin/latest
    node . run resetdeps

  • 8. Wait For Release Tags

    Warning:
    The remaining steps all require the GitHub tags and releases to be created first. These are done once this PR has been labelled with autorelease: tagged.

    Release Please will run on the just merged release commit and create GitHub releases and tags for each package. The release bot will will comment on this PR when the releases and tags are created.

    Note:
    The release workflow also includes the Node integration tests which do not need to finish before continuing.

    You can watch the release workflow in your terminal with the following command:

    gh run watch `gh run list -R npm/cli -w release -b latest -L 1 --json databaseId -q ".[0].databaseId"`

  • 9. Mark GitHub Release as latest

    Warning:
    You must wait for CI to create the release tags before running this step. These are done once this PR has been labelled with autorelease: tagged.

    Release Please will make GitHub Releases for the CLI and all workspaces, but GitHub has UI affordances for which release should appear as the "latest", which should always be the CLI. To mark the CLI release as latest run this command:

    gh release -R npm/cli edit v12.0.0-pre.0.0 --latest

  • 10. Open nodejs/node PR to update npm

    Warning:
    You must wait for CI to create the release tags before running this step. These are done once this PR has been labelled with autorelease: tagged.

    Trigger the Create Node PR action. This will open a PR on nodejs/node to the main branch.

    First, sync our fork of node with the upstream source:

    gh repo sync npm/node --source nodejs/node --force

    Then, if we are opening a PR against the latest version of node:

    gh workflow run create-node-pr.yml -R npm/cli -f spec=next-12

    For backport releases, you must target the correct Node branch using -f branch=<NODE_MAJOR>. Make sure you are targeting the right Node major version for this npm version.

    For example, this will create a PR on nodejs/node to the v16.x-staging branch:

    gh workflow run create-node-pr.yml -R npm/cli -f spec=next-12 -f branch=16

  • 11. Label and fast-track nodejs/node PR

    Note:
    This requires being a nodejs collaborator. This could be you!

    • Thumbs-up reaction on the Fast-track comment
    • Add an LGTM / Approval
    • Add request-ci label to get it running CI
    • Add commit-queue label once everything is green
    • For backport releases, comment on the PR asking the Node.js team to add dont-land-on-v<NODE_MAJOR> labels for Node versions where this npm version should not be included

@github-actions github-actions Bot force-pushed the release-please--branches--latest branch 3 times, most recently from d2c913a to 0b963e7 Compare April 14, 2026 17:23
@github-actions github-actions Bot changed the title chore: release 11.13.0-pre.0.0 chore: release 12.0.0-pre.0.0 Apr 15, 2026
@github-actions github-actions Bot force-pushed the release-please--branches--latest branch 23 times, most recently from 5f2c2fe to 889de7a Compare April 17, 2026 16:19
@github-actions github-actions Bot force-pushed the release-please--branches--latest branch 14 times, most recently from bcc9428 to a05053c Compare April 28, 2026 16:41
@github-actions github-actions Bot force-pushed the release-please--branches--latest branch 8 times, most recently from 9fc664f to bf85c4f Compare May 4, 2026 19:31
@github-actions github-actions Bot force-pushed the release-please--branches--latest branch 3 times, most recently from ead5d4d to 25bb66f Compare May 6, 2026 18:01
@github-actions github-actions Bot requested a review from a team as a code owner May 6, 2026 18:01
@github-actions github-actions Bot force-pushed the release-please--branches--latest branch 2 times, most recently from 3df0160 to d28615b Compare May 6, 2026 18:42
@github-actions github-actions Bot force-pushed the release-please--branches--latest branch from d28615b to d587498 Compare May 6, 2026 18:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

autorelease: pending

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants